feat: implement authentication state management with zustand #25
Merged
zakkiyyat merged 1 commit intoMixMatch-Inc:mainfrom Aug 23, 2025
Merged
feat: implement authentication state management with zustand #25zakkiyyat merged 1 commit intoMixMatch-Inc:mainfrom
zakkiyyat merged 1 commit intoMixMatch-Inc:mainfrom
Conversation
…grate react-query for data fetching
zakkiyyat
approved these changes
Aug 23, 2025
Contributor
zakkiyyat
left a comment
zakkiyyat
left a comment
There was a problem hiding this comment.
Perfect, exactly what we need! Thanks for the effort.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This establishes the application’s core data flow by combining Zustand for lightweight global UI state with TanStack Query for server-state management, including data fetching, caching, and invalidation. The setup introduces a central authStore, a configured QueryClientProvider, and custom hooks for server interactions, ensuring a clear separation of concerns and a resilient, responsive data layer.
closes #10